Aminet 7/Aminet 7 - August 1995.iso/Aminet/text/misc/GeekV47_11.lha/geek.doc

Text File | 1995-04-04 | 11.6 KB | 306 lines

Introduction
------------

This little tool allows you to encode or decode your personal geek code. If
you do NOT know what the geek code is, please refer to the chapter about
"The Code of the Geeks".

There are a few restriction to the original code:

If you use brackets such as "()" or the "wannabe" code ">" you have to
preclude the following code with the codesign itself. That means:
Instead of
       C++(---)
use
       C++(C---)

and instead of
       C-->+++
use
       C-->C+++

Another restriction is that some (just a small number) codes won't work
properly - these are the codes with "#" in the original encoding. So you
cannot use
       p3+
to show that you always have 3 pens/pencils AND a calculator with you. Use
       p3(p+)
instead.
All doubled codes such as sxxx:xxx have the same problem - you cannot (yet)
mix
       s+++:--
You COULD if you wanted change the encoding scheme to split "s" up into:

s+++
s++
s+
a.s.o.  with the corresponding HEIGHT parameters and
s:+++
s:++
s:+
a.s.o.  with the corresponding SIZE parameters.
Of course this would be a bit of the original encoding. (NOTE: since V11.03
this change has been made to geekcode.txt! So you can use s+++ and s:--)

Another change has been made to the original encoding: the Unix-section has
already been split up into the UNIX-SYSTEM (UB, UL a.s.o.) and the
UNIX-RATING (U+++, U-- a.s.o.) - compare the original GeekCode to the one
supplied as your codefile.

Please note that detection of the geek's gender is only correct if your
geekcode.txt (configfile) does not allow other gender codes than those
STARTING with x/y or z OR STARTING with "!" and continuing with x/y/z. The
original code follows this rule - you _can_ use something else but Output
of "This Geek is..." might be wrong then.

Usage
-----
V1.0 of the GeekInterpreter just DECODES a given GeekCode, up from V1.71
it also allows you to encode your personal GeekCode.
If you want to decode a given geeky string just supply the interpreter
with your (maybe translated) encoding-file AND of course the code to
interpret, put a "gc=" in front of it:

     GeekInt <your_codefile> GC=<some_geeky_code_fragments>

If you do not set a codefile-name, this parameter defaults to
"geekcode.txt".

The code fragments must be seperated by blanks, therefor all of the line
starting from "gc=" will be taken as the code to interpret.

If you specify "HELP" as a parameter in the commandline, a short usage-text
will be printed.

Set "INFO" somewhere before your geek-fragments to get a verbose
information about every single code fragment.

You may redirect the output with ">" as usual.

NOTE: a word wrapping feature is built in. So output _may_ be a bit slower
      than usual - but you should never get broken words at the end of a
      line!



Coding Your Geekiness
---------------------

Up from V1.71 you can code your own GeekCode that can be spread via
networks, letters, television shows or spaghetti. Simply leave out
the GC-parameter and go ahead. The program will ask you questions till
either you give up, the computer crashes or you have suceeded in answering
every single one.
If the later is the case you will get a single (sometimes rather long) line
containing all information about your state as a real Geek. Copy this line
to a file, write it down or forget it - do whatever you want to do with it.
If you spread it, every geek out there reading it will know everything
about you. Well... nearly.

If you want to code your own GeekCode your CodeFile has to include a [code]
section as explained in the next chapter.

How to compile your personal code
---------------------------------

When entering your code you have to answer all questions, as stated before.
Before that you'll get a short introduction to all possible answers.
Usually you enter the corresponding number to the lines above. Sometimes
you could add brackets surrounding another number... or an "at"-sign (@),
a "dollar" ($), a "wannabe"-code (">") or even a specific value as in the
number of pens you carry along with you (p...).

You can enter "r" (or "R") to review the same page which can be helpful if
there are too many lines. Since Output is done via StdIO you can interrupt
it the usual ways (space... CTRL-S/Q a.s.o.)

The CodeFile
------------

You can easily put together your own codefile, maybe in your own language.
Simply follow these rules:

The first lines of your codefile MUST contain these text fragments:

_______start________
Pronome used for male geeks (e.g. his)
Pronome used for female geeks (e.g. her)
Pronome used in codefile (e.g. my)
Text to apply to this geek (e.g. This Geek)
Text to indicate geek is a female one (e.g. is a female one)
Text to indicate geek is a male one (e.h. is a male one)
Text to indiacte this is the geek's job (e.g. This is done for living)
Text to apply in "@"-cases (e.g. This may differ from case to case...)
Text to introduce bracket-cases (e.g. Sometimes this phrase is true:)
Text to introduce "wannabe"-cases (e.g. the following is desired:)
_______end________

(so first line must be something like "his", second st. like "her" a.s.o.)

After this header you have to type in all used code fragments. You may part
Sections with a [Section xxxxx] header which is ignored by the interpreter.
(So they are just for your overview)
Each section SHOULD start with its title (e.g. [Computer]) AND an
information (e.g. [Geeks DO use computers]) after which the code fragments
itselfs are set.
The interpreter reads the file line by line - that means your section's
title is ONE line (surrounded by "[]"), the information is ONE line (since
it is split up by the wordwrapper) - as well surrounded by "[]" - and each
code fragment starts with the CODE, one or more spaces and the explanation
of it. As an example section look at this:

______start_______
[Section test]   (is ignored)
[Test]
[This is just a test part with no further meaning]
                 (blank lines between [] and code are ignored)
q--   I really hate this document.
q-    I simply do not like this document.
q     I AM this document.
q+    I have written this document.
q++   I am God.
_____end_________

If you specify "Info" in the interpreter's commandline, the line
         [This is just a test part with no further meaning]
will be printed out after the title of your section
                            [Test]
- this only if you have given a valid code for this section such as

GeekI Info gc=q--

Blank lines are ONLY ignored between the section headers and the codes.
Do NOT use blank lines between codes!

NOTE: Remember not to use mixed codes such as sxxx:yyy (very tall/very
      fat), try to split it up.

HINT: try to write your code geeky... well: all occurences of the
      pronome given in the THIRD line are replaced with either the
      male or the female pronome (given in the first or second line),
      if your code fragments include information about the geek's sex.
      This is by default done with "x", "y" or "z".

Coding your own GeekCode: If you want to code your own GeekCode you have
      to include a [code] section in your codefile that consists of two
      lines preceeded by a "[code]" keyword:

_____start______
[code]
Explanation text for all possible answers
Question line (Prompt)
______end_______

      Have a look in the example "geekcode.txt" file. Remember to give the
      user enough information in the explanation line if you write your
      own codefile.




About the GeekInterpreter
-------------------------

The GeekInterpreter is (C) 1995 by Marc J. Führer. It may copied,
distributed, spoiled, misused, deleted, stuffed, wombled and sold for non
profite use only. You may NEVER ask ANY fee for copying it. You may NEVER
give money along with it to be allowed to copy (argl... what's going on
here?)...
The author (who might that be?) keeps all copyrights, on earth, on mars and
everywhere else. The author (who?) Forbid()s to change ANY part of the
interpreter or the author (still wondering...) itself. He (the author?)
Permit()s to include the GeekInterpreter in any kind of public domain
selection, CD or whatever as long as it's price does not get higher than
the one paid for a single AmiNet-CDR, a FredFish-CDR or any carrier
comparable to these.
The author (damned... somehow this sounds familiar) can be reached via
[e-mail]
 - if not, he cannot be reached via [e-mail] .




.....................................................................


The Code of the Geeks v2.1 by R.A.Hayden
----------------------------------------
July 18, 1994

The Geek Code is copyright 1993,1994 by Robert A. Hayden
<[e-mail]>. All rights reserved. You are free to
distribute this code in electronic format provided that the file remains
unmodified and this copyright notice remains attached.

So you think you are a geek, eh? The first step is to admit to yourself your
geekiness. No matter what anyone says, geeks are people too; geeks have
rights. So take a deep breath and announce to the world that you are a geek.
Your courage will give you strength that will last you forever.

How to tell the world you are a geek, you ask? Use the universal Geek code.
By joining the geek organization, you have license to use this special code
that will allow you to let other un-closeted geeks know who you are in a
simple, codified statement.

The single best way to announce your geekhood is to add your geek code to
signature file and announce it far and wide. But be careful, you may give
other geeks the courage to come out of the closet. You might want to hang on
to your copy of the code in order to help them along.

Instructions for the Code of the Geeks
--------------------------------------

The geek code consists of several categories. Each category is labeled with a
letter and some qualifiers. Go through each category and determine which set
of qualifiers best describes you in that category. By stringing all of these
'codes' together, you are able to construct your overall geek code. It is
this single line of code that will inform other geeks the world over of what
a great geek you actually are.

Some of the qualifiers will very probably not match with you exactly. Simply
choose that qualifier that MOST CLOSELY matches you. Also, some activities
described in a specific qualifier you may not engage in, while you do engage
in others. Each description of each qualifier describes the wide range of
activities that apply, so as long as you match with one, you can probably use
that qualifier.

Also, pay particular attention to case-sensitivity, there can be a big
difference between a 'u' and a 'U'.



() Variables

Geeks can seldom be quantified. To facilitate the fact that within any one
category the geek may not be able determine a specific rating, variables have
been designed to allow this range to be included.

@
for variable, said trait is not very rigid, may change with time or with
individual interaction. For example, Geeks who happen to very much enjoy Star
Trek: The Next Generation, but dislike the old 60's series might list
themselves as t++@.

()
for indicating "cross-overs" or ranges. Geeks who go from C+ to C---
depending on the situation (i.e. mostly "C+") could use C+(---). Another
example might be an m++(**). This would be a person who mostly listens to
classical music, but also has an extensive collection of other types of
works.

>
for 'wannabe' ratings. Indicating that while the geek is currently at one
rating, they are striving to reach another. For example, C->++

$
Indicates that this particular category is done for a living. For example,
UL+++$ indicates that the person utilizes unix and gets paid for it. Quite a
lucky geek, for sure.

@ is different from () in that () has finite limits within the category,
while @ ranges all over.